-
Notifications
You must be signed in to change notification settings - Fork 80
fix(deps): update dependency next to v15.4.7 [security] #1488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
sepolia
Choose a base branch
from
renovate/npm-next-vulnerability
base: sepolia
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for GitHub.
|
da585f7
to
bc10e82
Compare
bc10e82
to
1db459c
Compare
1db459c
to
f74f692
Compare
f74f692
to
ae564cd
Compare
ae564cd
to
7319ec7
Compare
7319ec7
to
233f9c9
Compare
233f9c9
to
efbb6c6
Compare
efbb6c6
to
ddae02b
Compare
ddae02b
to
26cabf7
Compare
26cabf7
to
fe27dab
Compare
fe27dab
to
826914b
Compare
826914b
to
43b37bb
Compare
43b37bb
to
5c06917
Compare
5c06917
to
b2e36fd
Compare
6333183
to
0247dfc
Compare
0247dfc
to
f8c2478
Compare
f8c2478
to
f0ec502
Compare
f0ec502
to
baf3fff
Compare
baf3fff
to
0167508
Compare
0167508
to
26cf6a0
Compare
26cf6a0
to
32714d8
Compare
32714d8
to
bc90460
Compare
bc90460
to
f7462ef
Compare
f7462ef
to
ec09150
Compare
ec09150
to
ae06c55
Compare
ae06c55
to
6765434
Compare
6765434
to
b02270b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
15.1.4
->15.4.7
GitHub Vulnerability Alerts
CVE-2025-29927
Impact
It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.
Patches
15.2.3
14.2.25
13.5.9
12.3.5
Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.
Workaround
If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the
x-middleware-subrequest
header from reaching your Next.js application.Credits
CVE-2025-32421
Summary
We received a responsible disclosure from Allam Rachid (zhero) for a low-severity race-condition vulnerability in Next.js. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve
pageProps
data instead of standard HTML.Learn more here
Credit
Thank you to Allam Rachid (zhero) for the responsible disclosure. This research was rewarded as part of our bug bounty program.
CVE-2025-48068
Summary
A low-severity vulnerability in Next.js has been fixed in version 15.2.2. This issue may have allowed limited source code exposure when the dev server was running with the App Router enabled. The vulnerability only affects local development environments and requires the user to visit a malicious webpage while
npm run dev
is active.Because the mitigation is potentially a breaking change for some development setups, to opt-in to the fix, you must configure
allowedDevOrigins
in your next config after upgrading to a patched version. Learn more.Learn more: https://vercel.com/changelog/cve-2025-48068
Credit
Thanks to sapphi-red and Radman Siddiki for responsibly disclosing this issue.
CVE-2025-49826
Summary
A vulnerability affecting Next.js has been addressed. It impacted versions 15.0.4 through 15.1.8 and involved a cache poisoning bug leading to a Denial of Service (DoS) condition.
Under certain conditions, this issue may allow a HTTP 204 response to be cached for static pages, leading to the 204 response being served to all users attempting to access the page
More details: CVE-2025-49826
Credits
CVE-2025-55173
A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. The issue allowed attacker-controlled external image sources to trigger file downloads with arbitrary content and filenames under specific configurations. This behavior could be abused for phishing or malicious file delivery.
All users relying on
images.domains
orimages.remotePatterns
are encouraged to upgrade and verify that external image sources are strictly validated.More details at Vercel Changelog
CVE-2025-57752
A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. When images returned from API routes vary based on request headers (such as
Cookie
orAuthorization
), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug.All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.
More details at Vercel Changelog
CVE-2025-57822
A vulnerability in Next.js Middleware has been fixed in v14.2.32 and v15.4.7. The issue occurred when request headers were directly passed into
NextResponse.next()
. In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response.All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the
next()
function.More details at Vercel Changelog
Release Notes
vercel/next.js (next)
v15.4.7
Compare Source
v15.4.6
Compare Source
Core Changes
_error
page'sreq.url
can be overwritten to dynamic param on minimal mode (#82347)?dpl
to fonts in/_next/static/media
(#82384)Credits
Huge thanks to @devjiwonchoi, @ijjk, and @styfle for helping!
v15.4.5
Compare Source
v15.4.4
Compare Source
v15.4.3
Compare Source
v15.4.2
Compare Source
v15.4.1
Compare Source
v15.4.0
Compare Source
v15.3.5
Compare Source
v15.3.4
Compare Source
v15.3.3
Compare Source
v15.3.2
Compare Source
v15.3.1
Compare Source
Core Changes
Credits
Huge thanks to @kdy1 and @styfle for helping!
v15.3.0
Compare Source
Core Changes
<select>
styling for consistency: #76973029e8bd6-20250306
to0ca3deeb-20250311
: #769890ca3deeb-20250311
to6aa8254b-20250312
: #77033size
setting to preferences: #77027'seconds'
cache life profile: #77084next info
: #770596aa8254b-20250312
to5398b711-20250314
: #77129useLightningcss
option tostyled-jsx
correctly: #77008useErrorOverlayReducer
: #77205revalidate*
: #76885revalidate*
work when followed by a redirect in a route handler: #770905398b711-20250314
toc69a5fc5-20250318
: #77249"use cache"
caches when Draft Mode is enabled: #77141c69a5fc5-20250318
todb7dfe05-20250319
: #77295db7dfe05-20250319
to740a4f7a-20250325
: #77507740a4f7a-20250325
to313332d1-20250326
: #77527expireTags
/getExpiration
unnecessarily: #77570NEXT_PRIVATE_DEBUG_CACHE
env variable for cache handler debug logs: #77585nodejs
runtime in middleware: #77553"use cache"
revalidation logic out of incremental cache: #77577313332d1-20250326
to63779030-20250328
: #77643isrFlushToDisk
option to prevent writing optimized images to cache: #70645nodejs
runtime in middleware": #77690new URL()
forimages.remotePatterns
: #7769263779030-20250328
to040f8286-20250402
: #77742useLayoutEffect
warning if React 18 is used: #77737next start
: #77714TurbopackInternalError
s occur: #77660sideEffects
matching for non-relative globs: #77693issueCount
from non-asyncerrors
array: #77821refreshTags
andgetExpiration
: #77779"use cache"
wrapper: #77827searchParams
access in"use cache"
triggers error when caught: #77838getSourceFile
instead offileExists
to check file existence: #77863040f8286-20250402
to33661467-20250407
: #77899next/*
entrypoints: #77844Example Changes
canary
version: #77754Misc Changes
charset=utf-8
in data-url source maps: #77112react-refresh
as a dependency of plugin: #77142swc_core
tov16.6.0
: #77155swc_core
tov16.6.2
: #77194.minify()
of lightningcssStyleSheet
: #77313swc_core
and userayon
instead ofchili
: #77338copy_dir
concurrency to avoid running out of file descriptors: #77468swc_core
tov16.10.0
: #77489launch.json
to improve debugging in VSCode: #76559bun
and other package manager: #77633--js-build
as option instead of--no-js-build
: #77686Metadata and OG images
page: #74077Upgrade
page: #77717Examples
toGuides
: #77722swc_core
tov19.0.0
: #77669Vc
in a struct: #77756instrumentation-client
follow up: #77752styled-components
: #77736use server
and update examples: #77770use server
and update examples": #77771hygiene
if mangling is disabled: #77815Deep Dive
section placeholder: #77724await import("path")
in static analysis: #77811import_map
option ofswc_emotion
correctly: #71776swc_core
tov21.0.1
: #77918Getting Started
Section: #77921Credits
Huge thanks to @raunofreiberg, @huozhi, @ijjk, @timneutkens, @gaojude, @leerob, @mezotv, @bgw, @samcx, @ztanner, @sokra, @mischnic, @wbinnssmith, @kdy1, @unstubbable, @ahabhgk, @ScriptedAlchemy, @SukkaW, @wyattjoh, @eps1lon, @Amirroid, @Netail, @lubieowoce, @gnoff, @jackwilson323, @acdlite, @sbougerel, @kevva, @kasperpeulen, @Cy-Tek, @dvoytenko, @husseinraoouf, @isBatak, [@iamkd](https://redirect.
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.